[Offline Pages] We should add UMA for connection when attempting a request |
||||
Issue descriptionWhile looking at UMA, we decided it would be helpful if we checked the connection at the time we started a request, and put that out when we put out failure UMA to see if our failures are correlated with the network type.
,
Feb 7 2017
What kind of UMA are you thinking of?
,
Feb 28 2017
The work here is to remember the effective (NQE) connection type at request start, and when a request fails, emit a new UMA for effective network connection of failed request. This is a good fixit candidate.
,
Apr 25 2017
,
Apr 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/49ce38e06e2307125474c6e9f2db0f47ae45b3e1 commit 49ce38e06e2307125474c6e9f2db0f47ae45b3e1 Author: petewil <petewil@chromium.org> Date: Wed Apr 26 17:09:33 2017 Add UMA for network type at request start BUG= 673927 Review-Url: https://codereview.chromium.org/2840083002 Cr-Commit-Position: refs/heads/master@{#467355} [modify] https://crrev.com/49ce38e06e2307125474c6e9f2db0f47ae45b3e1/components/offline_pages/core/background/request_coordinator.cc [modify] https://crrev.com/49ce38e06e2307125474c6e9f2db0f47ae45b3e1/components/offline_pages/core/background/request_coordinator.h [modify] https://crrev.com/49ce38e06e2307125474c6e9f2db0f47ae45b3e1/components/offline_pages/core/background/request_coordinator_unittest.cc [modify] https://crrev.com/49ce38e06e2307125474c6e9f2db0f47ae45b3e1/tools/metrics/histograms/histograms.xml
,
Apr 28 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dim...@chromium.org
, Dec 14 2016Status: Assigned (was: Untriaged)