Remove Net.Daily* UMA |
|||||
Issue descriptionOnce we have new UMA capturing data usage measured at the HTTP layer, we should remove any code used for capturing the Net.Daily* histograms. These histograms are not that reliable (as they are only reported for users running Chrome in multiple consecutive days) and support for them has been disabled from the Flywheel UMA dashboard. (We should keep them until there are reasonable replacements, though, so we can spot check on the overall UMA dashboard.)
,
Nov 8 2017
,
Dec 12 2017
mdw and bengr, crbug.com/689659 (marked as fixed) tracks the new HTTP histograms. There are histograms for original length and content length, but no histograms for the difference between content length and original (this can be added if it is necessary), feel free to re-open the bug. It might be good to read the last few comments in the bug explaining why certain histograms are empty. My recommendation for histograms moving forward is to keep the following histograms: Net.HttpContentLengthV2* (the new histograms) Net.HttpContentLengthCacheable Net.HttpContentLengthCacheable24Hours Net.HttpContentLengthCacheable4Hours and to remove the other content length histograms: Net.Daily[Original]ContentLength* (e.g. Net.DailyContentLength_DataReductionProxyEnabled; there are about 40 of these, I can provide an exhaustive list if needed) Net.HttpContentLengthDifferenceWithValidOCL.LoFiOn Net.HttpOriginalContentLengthWithValidOCL Net.HttpOriginalContentLengthWithValidOCL.LoFiOn Net.HttpContentLength Net.HttpContentLengthDifference Net.HttpContentLengthDifferenceWithValidOCL Let me know if I should proceed with removing these, or if various metrics reports/dashboards need to be updated first.
,
Jan 30 2018
Refreshed during triage.
,
Mar 21 2018
The plan sgtm, except I don't know why we have the *Cacheable* histograms. Verify with mdw@ as he's a significant consumer before proceeding.
,
Apr 16 2018
SGTM - seems fine to me to remove the old ones per Ryan's recommendation in #3. (BTW, Ben -- it would have been faster for you to CC me on the bug as I am generally not that good at noticing references to my LDAP in random bug comments :-)
,
Apr 16 2018
,
Jun 22 2018
Done |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bengr@chromium.org
, Apr 30 2017Owner: ajo@chromium.org
Status: Assigned (was: Untriaged)