influxdata/telegraf
Ver no GitHubConfiguration option to drop oldest or newest data in the buffer when buffer is full
Open
#15.217 aberto em 24 de abr. de 2024
feature requesthelp wantedsize/m
Métricas do repositório
- Stars
- (9.892 stars)
- Métricas de merge de PR
- (Mesclagem média 2d 12h) (136 fundiu PRs em 30d)
Description
Use Case
Similar to https://github.com/influxdata/telegraf/issues/15208
(accommodating temporary high-write bursts to and influxdb instance)
Sometimes the newest data is more important to keep than the oldest data (if your computer failed, would you care more about what happened right before the failure or 5 minutes before the failure?)
Sometimes the oldest data is more important to keep than the newest data (ex: which events happened first in this very large burst of events?)
Expected behavior
I expected to see a configuration option like "buffer_drop_strategy" which would default to "drop_oldest".
Actual behavior
No configuration option to specify which metrics (newest or oldest) are dropped from the buffer.
Additional info
No response