Add UMA to track when data reduction proxy is unreachable, but internet is reachable. |
|||||||||
Issue descriptionUsers on Android are shown an error message to warn them that data savings might be limited. Pertinent code: https://cs.chromium.org/chromium/src/components/data_reduction_proxy/core/browser/data_reduction_proxy_bypass_stats.cc?sq=package:chromium&rcl=1467890327&l=204
,
Oct 28 2016
Do we record UMA when the warning message is shown?
,
Dec 1 2016
,
Dec 22 2016
Megan, as we expand on our warning messages, please track with UMA, starting with this issue.
,
Oct 4 2017
Making available for reassignment
,
Dec 1 2017
tbansal@: this is related to your work to make the drp more robust.
,
Dec 21 2017
,
Jan 4 2018
Issue 778327 has been merged into this issue.
,
Jan 4 2018
,
Feb 20 2018
Refreshed during triage.
,
Mar 29 2018
This is a pretty vague bug -- it is not clear why we need this. Also, there might be cases where only one of the many DRP proxies are reachable. Having said that, we have DataReductionProxy.WarmupURL.ProxySchemeUsed which indicates the proxy that was used to fetch the warmup probe. We also have DataReductionProxy.WarmupURL.HttpResponseCode which indicates the response code of the warmup fetch. It's possible to do dremel analysis to find reports where all the samples in DataReductionProxy.WarmupURL.ProxySchemeUsed belong to bucket "Direct". This would indicate that probe to all the DRP proxies failed. Joining that would user reports where DataReductionProxy.WarmupURL.HttpResponseCode has all samples in bucket 204 would indicate that the fetching of the probe URL succeeded directly. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by bengr@chromium.org
, Jul 19 2016