-
Notifications
You must be signed in to change notification settings - Fork 4
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
statsd: aggregate metrics from a chunk in batch #146
base: aiven-release-v1.32.0
Are you sure you want to change the base?
Conversation
Process all metrics in a chunk together. This is necessary for custom Prometheus-like histogram metrics. For example, when creating an `http_response_duration_seconds` metric with buckets 1...100 and a flush interval in Telegraf set to 30 seconds, the old version of the code would process each sample separately. If a flush interval occurred, only the processed metrics would be flushed with the current timestamp. The next metrics would be flushed in the following interval with a different timestamp (+30s), causing issues with histogram calculation. In the current version, all samples are processed together.
88cd0d9
to
983389e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
I just want someone with more go knowledge to also review before merging
We should really be making changes upstream and not in our fork. Leads to maintenance nightmare. |
Ideally we could get these changes merged upstream and get our fork closer to head of upstream cause we are lagging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to be really annoying and request changes here as we don't really want to be adding features to our fork that are not in upstream? At least we should try upstream first.
We already have a nightmare to sync with upstream (#144) :sadcat: but I agree, that things might be good for others it should be pushed to upstream, and I'm already working on it, but it needs some time... |
Process all metrics in a chunk together.
This is necessary for custom Prometheus-like histogram metrics. For example, when creating an
http_response_duration_seconds
metric with buckets 1...100 and a flush interval in Telegraf set to 30 seconds, the old version of the code would process each sample separately. If a flush interval occurred, only the processed metrics would be flushed with the current timestamp. The next metrics would be flushed in the following interval with a different timestamp (+30s), causing issues with histogram calculation. In the current version, all samples are processed together.Required for all PRs
resolves #