Skip to content

1.0: in_tail: Add read_bytes_limit_per_second description #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ashie merged 1 commit into from
May 29, 2021
Merged

1.0: in_tail: Add read_bytes_limit_per_second description #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions input/tail.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,20 @@ The number of lines to read with each I/O operation.

If you see `chunk bytes limit exceeds for an emitted event stream` or similar log with `in_tail`, set a smaller value.

### `read_bytes_limit_per_second`

| type | default | version |
|:--------|:---------------|:--------|
| size | -1 (unlimited) | 1.13.0 |

The number of reading bytes per second to read with I/O operation.

This value should be equal or greater than 8192.

If you work with a big cluster with high volume of log, you can use this parameter
to avoid network saturation and make it easier to calculate the max throughput per node.
To restrict shipping log volumes per second, set a positive number.

### `multiline_flush_interval`

| type | default | version |
Expand Down