Consider re-bucketing of metrics.SecondsTimer data for our use cases |
|||||
Issue description
We're adding a whole lot of metrics.SecondsTimer{Decorator}s to our code for issue 667171. As akeshet@ points out, the underlying distribution metric's default buckets may not be well suited for some of these metrics. For example, by default, the first bucket is 0-1 second, growing geometrically from there (second bucket is 1 - 1.1 and so on).
ts_mon provides the flexibility of rebucketing for just such a use case: http://shortn/_aQDyZTA4T5
This bug is an AI to observe the data we get from the various SecondsTimers we're adding and decide whether we want to rebucket some of them.
Snooze for 1/2 month while we collect data to make this decision ;)
,
Nov 23 2016
We already do have a custom bucketer. The real question is, do we need sub-second buckets: http://shortn/_7a2YJzbnGl
,
Nov 23 2016
,
Nov 29 2016
,
Jun 28 2017
akeshet@ actually did something like this recently, so now we can scale the buckets arbitrarily.
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pprabhu@chromium.org
, Nov 23 2016