Bug #24387
Telemetry buckets need to be set in seconds, not miliseconds
Pull request:
Fixed in Releases:
Found in Releases:
Description
I was hitting an issue with the statsd buckets. All the requests were falling into all buckets we had, which was strange. It turns out the buckets need to be defined in seconds, not miliseconds.
Associated revisions
History
#1
Updated by The Foreman Bot over 1 year ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5874 added
#2
Updated by Lukas Zapletal over 1 year ago
- Found in Releases 1.18.0 added
- Fixed in Releases 1.20.0 added
#3
Updated by Ivan Necas over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset 69edab723b4f7baa66296e1b2f6397802ccd6f4b.
#4
Updated by Tomer Brisker about 1 year ago
- Category set to Logging
Fixes #24387 - defined telemetry buckets in seconds
Also, add more granular buckets, the scale inspired by
https://github.com/prometheus/client_golang\
/blob/1ba60c7d585/prometheus/histogram.go#L59