dom
/
telegraf
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document the pros and cons of increasing the metric_buffer_limit

This commit is contained in:
Daniel Nelson 2019-09-09 17:50:46 -07:00
parent f041ace365
commit 5dcd0daa42
No known key found for this signature in database
GPG Key ID: CAAD59C9444F6155
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/CONFIGURATION.md
View File

@ -112,7 +112,9 @@ The agent table configures Telegraf and the defaults used across all plugins.
This controls the size of writes that Telegraf sends to output plugins. This controls the size of writes that Telegraf sends to output plugins.
- **metric_buffer_limit**: - **metric_buffer_limit**:
Maximum number of unwritten metrics per output. Maximum number of unwritten metrics per output. Increasing this value
allows for longer periods of output downtime without dropping metrics at the
cost of higher maximum memory usage.
- **collection_jitter**: - **collection_jitter**:
Collection jitter is used to jitter the collection by a random [interval][]. Collection jitter is used to jitter the collection by a random [interval][].

4
internal/config/config.go
View File

@ -257,7 +257,9 @@ var agentConfig = `
## This controls the size of writes that Telegraf sends to output plugins. ## This controls the size of writes that Telegraf sends to output plugins.
metric_batch_size = 1000 metric_batch_size = 1000
## Maximum number of unwritten metrics per output. ## Maximum number of unwritten metrics per output. Increasing this value
## allows for longer periods of output downtime without dropping metrics at the
## cost of higher maximum memory usage.
metric_buffer_limit = 10000 metric_buffer_limit = 10000
## Collection jitter is used to jitter the collection by a random amount. ## Collection jitter is used to jitter the collection by a random amount.