Skip to content
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.

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

feat(processors): Traffic shaper processor plugin to shape uneven distribution of incoming metrics #15353

Closed
lakshmansai opened this issue May 14, 2024 · 1 comment
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@lakshmansai
Copy link

Use Case

An in-memory traffic shaper processor which evens out traffic so that output traffic is uniform

We use telegraf as a proxy and we receive data that is spiky in nature, in our every 10 minute we receive a spike and this affects our downstream systems since it needs to also process at the same rate, this leads to wastage of resource since the cpu, memory needs to be provisioned for peaks

Screenshot showing spiky nature of data
Screenshot 2024-05-10 at 2 32 43 PM

Expected behavior

Actual behavior

We have implemented a traffic shaper plugin in telegraf which evens out the spike and help us maintain a steady rate.

Example post using traffic shaper plugin we can see after 00:00 the traffic became uniform

traffic_distribution

Additional info

No response

@powersj
Copy link
Contributor

powersj commented May 16, 2024

Hi,

After discussing with the team, we would prefer that rate limiting like this occur in outputs instead of a processor. We have an open issue for this in: #14802 That is where I would want to continue this discussion.

The processor solution unfortunately adds a second buffer, which introduces another set of issues. You can see some examples of this #802 for a way to maintain the buffer outside of memory via a WAL and how to control the buffer itself with #15208 and #15217.

As such we do not wish to add a processor, but would take a PR to look at output rate limiting. I will close this issue and the PR.

@powersj powersj closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
2 participants