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

Allow unique flush_jitter values for different output plugins #6569

Closed
dbutler-starry opened this issue Oct 23, 2019 · 0 comments · Fixed by #6603
Closed

Allow unique flush_jitter values for different output plugins #6569

dbutler-starry opened this issue Oct 23, 2019 · 0 comments · Fixed by #6603
Labels
feature request Requests for new plugin and for new features to existing plugins
Milestone

Comments

@dbutler-starry
Copy link
Contributor

Feature Request

Opening a feature request kicks off a discussion.

Proposal:

Allow unique flush_jitter values for different output plugins

Current behavior:

Every output plugin is forced to use the same flush_jitter

Desired behavior:

Specify flush_jitter per output plugin in the config file. If no custom flush_jitter is defined for a plugin, use the default flush_jitter (similar to how flush_interval works now)

Use case:

This would be useful for forwarding collections to multiple output plugins that flush at different flush_intervals. It would be nice to be able change flush_jitter per plugin, otherwise each output plugin is forced to use a flush_jitter that fits within the smallest flush_interval

@danielnelson danielnelson changed the title Allow unique flush_interval values for different output plugins Allow unique flush_jitter values for different output plugins Oct 23, 2019
@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Oct 23, 2019
@danielnelson danielnelson added this to the 1.13.0 milestone Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

2 participants