New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 668271 link

Starred by 3 users

Issue metadata

Status: Archived
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue 667171



Sign in to add a comment

Consider re-bucketing of metrics.SecondsTimer data for our use cases

Project Member Reported by pprabhu@chromium.org, Nov 23 2016

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 ;)
 
Blockedon: 667171
We already do have a custom bucketer. The real question is, do we need sub-second buckets: http://shortn/_7a2YJzbnGl
Cc: pho...@chromium.org

Comment 4 by autumn@chromium.org, Nov 29 2016

Labels: -current-issue
Status: Fixed (was: Assigned)
akeshet@ actually did something like this recently, so now we can scale the buckets arbitrarily.

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment