We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I use the numeric_monitor plugin with a timer value of 1 second, it fires every two seconds. This is the config block I use:
<match stats.**> type numeric_monitor aggregate tag input_tag_remove_prefix stats tag_prefix stats2 monitor_key count count_interval 1s output_per_tag yes
This posts a new output every 2 seconds, and the counts add up. So it's running every 2 seconds instead of every second.
Is this supposed to work? Does Ruby support sub-second timers? If not, please make it an error to use 1 second.
The text was updated successfully, but these errors were encountered:
fix issue #11: flush right after interval
30cf9dd
Fixed this bug and released v0.1.8. @LanceNorskog Please reopen this issue if you still have problems!
v0.1.8
Sorry, something went wrong.
No branches or pull requests
When I use the numeric_monitor plugin with a timer value of 1 second, it fires every two seconds.
This is the config block I use:
<match stats.**>
type numeric_monitor
aggregate tag
input_tag_remove_prefix stats
tag_prefix stats2
monitor_key count
count_interval 1s
output_per_tag yes
This posts a new output every 2 seconds, and the counts add up. So it's running every 2 seconds instead of every second.
Is this supposed to work? Does Ruby support sub-second timers? If not, please make it an error to use 1 second.
The text was updated successfully, but these errors were encountered: