influxdata / influxdata/telegraf
Configuration option to send Buffer in newest-to-oldest order
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
Use Case
The telegraf buffer is sometimes used to temporarily accommodate high write rates to an influxdb instance.
Sometimes it is preferred to see the newest data in influxdb first and backfill the older data until the production rate decreases.
Expected behavior
I expected to see a configuration option for the buffer to allow it to flush the newest data first instead of the oldest data.
Actual behavior
Only the oldest data is flushed first.
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the buffer configuration and the implementation that determines flush order. Check how existing buffer options are documented and tested before deciding how a newest-first setting should behave. Done means the option is configurable, newest data is flushed first when enabled, and existing oldest-first behavior remains unchanged by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100