You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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
The text was updated successfully, but these errors were encountered: