-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Option to flush buffer on request #5120
Labels
Comments
glinton
added
the
feature request
Requests for new plugin and for new features to existing plugins
label
Dec 6, 2018
By flush, you mean to flush to the endpoint and not drop, correct? |
Yes. On request telegraf could try to flush buffered data to the endpoint (e.g. InfluxDB). |
3 tasks
This already happens automatically with a graceful shutdown , right? Sent with GitHawk |
Yes, during a normal shutdown where the output is able to write, the full metric buffer is written. |
pingleig
added a commit
to pingleig/amazon-cloudwatch-agent
that referenced
this issue
Dec 8, 2020
* Telegraf already listen to signals and close output plugins for graceful shutdown, but we are forking the agent as another process inside container without forwarding singals. * Our output plugins does not flush on `Write` call so `SIGUSR1` force flush does not work in cloudwatch-agent as native telegraf influxdata/telegraf#5120
yimuniao
pushed a commit
to aws/amazon-cloudwatch-agent
that referenced
this issue
Dec 9, 2020
* Telegraf already listen to signals and close output plugins for graceful shutdown, but we are forking the agent as another process inside container without forwarding singals. * Our output plugins does not flush on `Write` call so `SIGUSR1` force flush does not work in cloudwatch-agent as native telegraf influxdata/telegraf#5120
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature Request
To have an option to flush telegraf buffer on request. For example, telegraf could (attempt to) flush the buffer on, e.g. USR1 IPC signal.
Use case:
There are monitoring scenarios where the desirable behavior would be to flush the buffered data based on time or size most of the time, but on rare occasions, on some event, flush it ASAP.
The text was updated successfully, but these errors were encountered: