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

Option to flush buffer on request #5120

Closed
r0nald opened this issue Dec 6, 2018 · 4 comments · Fixed by #7366
Closed

Option to flush buffer on request #5120

r0nald opened this issue Dec 6, 2018 · 4 comments · Fixed by #7366
Assignees
Labels
area/agent feature request Requests for new plugin and for new features to existing plugins

Comments

@r0nald
Copy link

r0nald commented Dec 6, 2018

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.

@glinton glinton added the feature request Requests for new plugin and for new features to existing plugins label Dec 6, 2018
@glinton
Copy link
Contributor

glinton commented Dec 6, 2018

By flush, you mean to flush to the endpoint and not drop, correct?

@r0nald
Copy link
Author

r0nald commented Dec 7, 2018

Yes. On request telegraf could try to flush buffered data to the endpoint (e.g. InfluxDB).

@voiprodrigo
Copy link
Contributor

This already happens automatically with a graceful shutdown , right?

Sent with GitHawk

@danielnelson
Copy link
Contributor

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
area/agent feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants