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

-remoteWrite.rateLimit for vmagent #2175

Open
1 task done
Olliferdl opened this issue May 24, 2023 · 1 comment
Open
1 task done

-remoteWrite.rateLimit for vmagent #2175

Olliferdl opened this issue May 24, 2023 · 1 comment
Assignees
Labels
feature Feature request

Comments

@Olliferdl
Copy link

Description

When there is a lot of buffered data, from a lot of clients, being sent all at once after the pmm-server was down or unreachable for a while, the server or network can be overwhelmed.
This could be counteracted by setting a rate limit for the vmagent.

Suggested solution

Allow configuration of the vmagent launch arguments somewhere

Additional context

https://docs.victoriametrics.com/vmagent.html#advanced-usage:~:text=%2DremoteWrite.rateLimit%20array,the%20remote%20storage

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Olliferdl Olliferdl added the feature Feature request label May 24, 2023
@BupycHuk
Copy link
Member

BupycHuk commented Jul 7, 2023

Hi @Olliferdl, we are implementing this feature in scope of https://jira.percona.com/browse/PMM-9374, so there will be a possibility to pass VMAGENT_* env variables to PMM Server and this will be available on all vmagents connected to the PMM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request
Projects
None yet
Development

No branches or pull requests

3 participants