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

Issue 848356 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Metrics Documentation - Discourage Incrementing Sequentially

Project Member Reported by mpear...@chromium.org, May 31 2018

Issue description


e.g.,
https://chromium-review.googlesource.com/c/chromium/src/+/1073683/2/content/browser/network_service_instance.cc#48

This is an anti-pattern that we see periodically, where users keep a count of something and emit something to a histogram ever time they increment the count.  This makes the histograms hard to interpret.  For example, the dashboard's summary statistics will be meaningless.

I'm not sure if this is common enough or if we have a good general purpose answer for people who want to do this about what they should do instead.  I think I've seen different solutions (emit a single count, and do analysis of the UMA logs where you aggregate per client; emit the total periodically, like every hour; instead emit ratio periodically; ...)



 

Sign in to add a comment