-
Notifications
You must be signed in to change notification settings - Fork 99
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
When statsd wait metric it send 0 to backend #296
Comments
Hi This is controlled by the By default it's |
my config: mode = 'legacy' global_prefix = 'stats' prefix_counter = 'counters' With this config stated send 0 every 1 second. |
It's the interaction of two separate parts - flush interval and metric expiry. The flush interval is how often metrics are aggregated and sent upstream, and is 1 second by default. The expiry interval is how long a metric needs to receive no data before it stops being sent upstream. If you were to not send and metrics for 30 seconds, you would see your last value, 29 zeros, and then it would stop sending. When I look at your graph, I can see there are periods of at least 30 seconds where the value appears to be 0 (I'm assuming all your non-zero values are > 400, and not 1 or 2 where it may not be visible on the graph). The rendered interval also appears to be 10 seconds. This makes me suspect there's also zeros being added on display, but that's speculation. edit: expiry happens on flush, after sending metrics upstream. That's why a value of -1 will cause them to expire immediately. |
Thanks for the explanation, It's working! |
When statsd wait metric it send 0 to backend (go-carbon)
How I can don't send 0 to backend?
The text was updated successfully, but these errors were encountered: