influxdata/telegraf

Configuration option to send Buffer in newest-to-oldest order

Open

#15,208 opened on Apr 22, 2024

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Go (9,892 stars) (4,161 forks)batch import
feature requesthelp wantedsize/m

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

Tech stack
go
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingUnderstanding of Telegraf's buffer internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
The issue requests a configuration option to flush the buffer in newest to oldest order. Start by examining the buffer implementation in Telegraf, likely in the 'agent' or 'internal' directories. Look for the current buffer flush logic, which currently sends oldest first. A new config option (e.g., 'buffer flush order') could be added to reverse the order. No existing pull requests are linked. Check comments for any maintainer feedback on feasibility.