Session.TotalDuration metric has artificial spike at 3 seconds on Windows platform. |
|||
Issue descriptionThis is presumably due to the 3 second timeout logic in the ChromeVisibilityObserver, which is not being subtracted from the final reported session duration.
,
Oct 3 2016
Hopefully this is fixed. I'll be monitoring metrics this week to see if the data looks like it makes more sense.
,
Oct 5 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Oct 3 2016