Collect data usage metrics in Chrome feedback reports |
||||||||||||||||
Issue descriptionFrom: https://productforums.google.com/forum/#!msg/chrome/q-XfCaApYBo/4Ncucux3CwAJ This user is saying that Chrome used over 5GB of "background data" overnight. I am assuming that he checked this using the Android data usage menu. I'm very surprised to hear there's no way for us to get any useful information on what happened in this case -- even if the user files a bug report, we won't get the information we need to track down the problem. Broadly speaking we see many cases where users report (e.g., via in-app feedback) that Chrome uses too much data. Generally these are not actionable as we have no other information to go on. It would be useful to have these bug reports contain information on data usage, e.g., broken down by network type as well as the type of data (browsing, UMA, Omaha, Sync, etc) It would also be nice for this information to appear in chrome://net-internals#bandwidth.
,
Oct 19 2016
,
Oct 19 2016
Note that user feedback reports on Android (M-56+) now have the UMA metrics attached as gzipped json file (https://bugs.chromium.org/p/chromium/issues/detail?id=651621). So, that should help in debugging this provided Chrome has the right UMA metrics for data usage. However, we need to make sure that the number of bytes reported as "Untagged" are as few as possible. In the past couple of cases, the debugging was impossible because 90% of the bytes in the UMA were untagged (https://bugs.chromium.org/p/chromium/issues/detail?id=655749).
,
Oct 28 2016
tbansal: Will you follow-up on this or will rajendrant?
,
Oct 28 2016
Since we are now collecting data use histograms in user feedback reports, is this bug still relevant?
,
Jan 12 2017
,
Jan 23 2017
Hi, I'm re-opening this since it seems that the UMA data reported in Feedback reports is only since the last launch of Chrome (right, Raj?) If so, is there any way for us to send back UMA data prior to this, or is that not technically possible (e.g., since UMA data is only held in memory)? I have two other ideas: 1) Why can't the Feedback report send back data usage counters -- not UMA -- going back ~30 days (assuming Chrome is already persisting that state locally (e.g. for the UI)? 2) If the Feedback report is not going to include a Gaia ID, can we include the UMA client ID in the report instead? This would at least allow us to look at the client's historical UMA data keyed off of that.
,
Jan 23 2017
Yes. Only UMA since last launch is held in memory and reported in feedback. Persistent histograms support (http://crbug.com/583440) could help. Its not clear when it would launch and how much UMA would be persisted. I will look at your other suggestions. Reporting UMA client ID when there is no GAIA ID, seems the best approach.
,
May 5 2017
Raj, any progress on this?
,
Oct 30 2017
,
Dec 19 2017
Any updates here? Can we close this bug?
,
Feb 7 2018
,
Feb 7 2018
,
Feb 7 2018
As noted in c#7 above, this bug tracks the work to get data usage breakdown of last 30 days. One option is: 1. Use prefs to store the data usage breakdown 2. Upload the prefs as part of histograms at time of Chrome startup.
,
Mar 27 2018
Refreshed during triage.
,
May 18 2018
,
May 22 2018
Refreshed during triage.
,
Jun 20 2018
As a first step, I am planning to add the following aggregated data use metrics for last two weeks. ThisWeekAggregate metrics will include breakdown for the last 7 days. LastWeekAggregate will be for the previous week. DataUse.ThisWeekAggregate.DownStream.Services.BackgroundKB [enumerated services] DataUse.ThisWeekAggregate.DownStream.Services.ForegroundKB [enumerated services] DataUse.ThisWeekAggregate.DownStream.UserTraffic.ContentType Breakdown of user traffic such as video/audio and whether tab/app in background/foreground. Similar metrics for DataUse.LastWeekAggregate.*.
,
Jul 7
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9e4ea078232b0643f78f6225fa1e7a22d3b649c2 commit 9e4ea078232b0643f78f6225fa1e7a22d3b649c2 Author: rajendrant <rajendrant@chromium.org> Date: Sat Jul 07 02:44:08 2018 Record weekly aggregated data use metrics This CL records aggregated data use for this week and the previous week. This is broken down by services traffic in foreground, background, and content-type of user initiated traffic. Only downstream data use is recorded. Bug: 630652 Change-Id: I16eb52ba3196b499c5d9fb6eae591df300fac15c Reviewed-on: https://chromium-review.googlesource.com/1122317 Commit-Queue: rajendrant <rajendrant@chromium.org> Reviewed-by: Ryan Sturm <ryansturm@chromium.org> Reviewed-by: Tarun Bansal <tbansal@chromium.org> Reviewed-by: Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#573143} [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/chrome/browser/page_load_metrics/observers/page_capping_page_load_metrics_observer.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/chrome/browser/previews/previews_infobar_tab_helper.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats_unittest.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_data_use_observer.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_data_use_observer_unittest.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_io_data.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_io_data.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_network_delegate.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_network_delegate.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_prefs.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_service.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_service.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/browser/data_reduction_proxy_test_utils.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/common/data_reduction_proxy_pref_names.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_reduction_proxy/core/common/data_reduction_proxy_pref_names.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_use_measurement/core/data_use_measurement.cc [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/components/data_use_measurement/core/data_use_measurement.h [modify] https://crrev.com/9e4ea078232b0643f78f6225fa1e7a22d3b649c2/tools/metrics/histograms/histograms.xml
,
Jul 18
,
Jul 20
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0106342e67d4eb9ba4ab6eca7af0548077606daa commit 0106342e67d4eb9ba4ab6eca7af0548077606daa Author: rajendrant <rajendrant@chromium.org> Date: Fri Jul 20 19:08:41 2018 Fix weekly aggregate recording in android Bug: 630652 Change-Id: Iaacf13e7a3680407a4ead0eb11554f13b17d36a6 Reviewed-on: https://chromium-review.googlesource.com/1142491 Reviewed-by: Ryan Sturm <ryansturm@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#576943} [modify] https://crrev.com/0106342e67d4eb9ba4ab6eca7af0548077606daa/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats.cc
,
Aug 14
Raj, did this make M69 branch? Is a merge needed?
,
Aug 14
Yes. Commit in #c21 needs to be merged. Requesting for merge.
,
Aug 14
This bug requires manual review: M69 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 14
+amineer@/benmason@ (Chrome on Android TPMs) for M69 merge review as cl listed at #21 is for Android.
,
Aug 15
Approved for merge into 69.
,
Aug 15
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/875fe7550cb041c6cf2ef38b456bca410559e64f commit 875fe7550cb041c6cf2ef38b456bca410559e64f Author: rajendrant <rajendrant@chromium.org> Date: Wed Aug 15 02:25:15 2018 Fix weekly aggregate recording in android Bug: 630652 Change-Id: Iaacf13e7a3680407a4ead0eb11554f13b17d36a6 Reviewed-on: https://chromium-review.googlesource.com/1142491 Reviewed-by: Ryan Sturm <ryansturm@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#576943}(cherry picked from commit 0106342e67d4eb9ba4ab6eca7af0548077606daa) Reviewed-on: https://chromium-review.googlesource.com/1174612 Reviewed-by: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/branch-heads/3497@{#635} Cr-Branched-From: 271eaf50594eb818c9295dc78d364aea18c82ea8-refs/heads/master@{#576753} [modify] https://crrev.com/875fe7550cb041c6cf2ef38b456bca410559e64f/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats.cc
,
Aug 15
|
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by bengr@chromium.org
, Jul 22 2016