You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.
I haven't a recipe for this yet; however, the situation is a metric, a counter, that emits hourly, just once. Several times in a 24 hour period, a metric for a given hour emits in the following hour.
This yields an hour without a metric, and an hour with a count of 2.0. I expect every hour to have a count of 1.0.
(Not my idea by the way to have an hourly metric, but it is what it is ...)
The Graphite project indicates that it honors the timestamp of the inbound metric. This suggests that the two metrics from brubeck are emitted with a timestamp of the same, in this case 10-second, bucket.
I can confirm that the metrics are sent at the proper time and received by brubeck at that time. I've added telemetry to log metric receipt, with timestamp and by regex, which logs the receipt of the metric by the statds sampler and can confirm that the metrics in question were received at the appropriate time.
My reporting interval is 10 seconds, and the expiry 7 seconds. I've varied this up to 20 seconds expiry without effect.
I will post more information as I have it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I haven't a recipe for this yet; however, the situation is a metric, a counter, that emits hourly, just once. Several times in a 24 hour period, a metric for a given hour emits in the following hour.
This yields an hour without a metric, and an hour with a count of 2.0. I expect every hour to have a count of 1.0.
(Not my idea by the way to have an hourly metric, but it is what it is ...)
The Graphite project indicates that it honors the timestamp of the inbound metric. This suggests that the two metrics from brubeck are emitted with a timestamp of the same, in this case 10-second, bucket.
I can confirm that the metrics are sent at the proper time and received by brubeck at that time. I've added telemetry to log metric receipt, with timestamp and by regex, which logs the receipt of the metric by the statds sampler and can confirm that the metrics in question were received at the appropriate time.
My reporting interval is 10 seconds, and the expiry 7 seconds. I've varied this up to 20 seconds expiry without effect.
I will post more information as I have it.
The text was updated successfully, but these errors were encountered: