-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/prometheusremotewriteexporter] Allow to set batch_send_deadline #32891
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/prometheusremotewrite
Is your feature request related to a problem? Please describe.
In a standalone Prometheus remote-write's configuration, you can set up a
queue_config
with many options. For instance:Currently in the
prometheusremotewriteexporter
you can only set the following:As we can't set the
batch_send_deadline
option, theprometheusremotewriteexporter
seems to perform remote-writes only each 60sec (can't find where it's set).If the remote-write backend have less HA replicas than the number of
prometheusremotewriteexporter
pushing replicas, and the remote-write backend try to elect a new replicas leader less than each 60sec, the HA backend will pick a new leader and the send metrics will be dropped.Describe the solution you'd like
Be able to define the remote-write frequency
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: